[WIP] feat: A vispy-based stage tracker #305
Conversation
…core-widgets into vispy_stage_recorder
fdrgsp
changed the title
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #305 +/- ##
==========================================
- Coverage 90.73% 86.30% -4.44%
==========================================
Files 85 87 +2
Lines 9233 9858 +625
==========================================
+ Hits 8378 8508 +130
- Misses 855 1350 +495 ☔ View full report in Codecov by Sentry. |
|
this is a pretty awesome feature @fdrgsp, and it would be good to get something like this in. For the sake of review, I think it would be helpful for me to get your thoughts on some high level things, such as what use cases this could serve, and also what the public API of the various objects should be. I know I can look at the code, but could you also comment here on the main objects and what they do? Does this build an image map of visited locations (hard to tell from your demo). Does it work with z positions? etc... basically, guide us a bit more through what your vision is here, in words |
In this very WIP PR I started thinking about a widget that tracks the stage movements and is able to record the positions (and move to new positions with double-click). The widget is named
StageTracker. To see an example of usage run thestage_tracker.pyexample.Screen.Recording.2024-06-24.at.8.03.00.PM.mov
NOTE: there is also a version named
StageRecorderthat is also adding the snapped images in the canvas. This requires more work on how to downsacale the images, etc... To see an example run thestage_recorder.pyexample.